OpenEdge Application Server:<br />Administration Web server and JSE configurations

Release 10.1A: OpenEdge Application Server:
Administration

Web server and JSE configurations

As shown in Figure 5-1, the WSA is implemented as a Java servlet that runs in the context of a JSE as a Web application. The JSE can run stand-alone (that is, with an integrated Web server), or in the context of an optional, separate Web server (such as Apache or IIS).

When the WSA runs within the context of a JSE or Web server, several WSA instances can run within the context of the WSA Web application (such as wsa1 and wsa2 shown in Figure 5-1). In addition to the WSA Web application other Web applications can run within the JSE, including additional WSA instances.

The configuration of a Web server-based WSA is:
Web server ( root ) 
    JSE ( web-server-context ) 
        WSA Web application ( wsa-webapp-context ) 
            WSA instance ( wsa-instance ) 
            ... 
        ... 
        Non-WSA Web application 
        ... 
    ... 
    Non-JSE Web resource, such as a static html page 
    ... 
... 
In the Web server-based WSA configuration:

There is a separate Web server.

The Web server comprises one or more JSEs (web-server-context) and one or more non-JSE Web resources, such as static HTML pages.

Each JSE comprises one or more WSA Web applications (wsa-webapp-context) and one or more non-WSA Web applications.

Each WSA Web application comprises one or more WSA instances (wsa-instance).

If the JSE runs stand-alone (that is, with an integrated Web server), the JSE-based WSA configuration is:
Stand-alone JSE ( root ) 
    WSA Web application ( wsa-webapp-context ) 
        WSA instance ( wsa-instance ) 
        ... 
    ... 
    Non-WSA Web application 
    ... 
In both these configurations, web-server-context, wsa-webapp-context, and wsa-instance appear in bold because they are components of the URL for accessing the WSA.